Microsoft Entra Connect End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Microsoft Entra Connect versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Microsoft Entra Connect 2.6.92.0 is supported, with no end-of-life or end-of-support date announced yet. The next Microsoft Entra Connect version to reach end of life is 2.5.79.0, on October 23, 2026. 12 of 19 tracked Microsoft Entra Connect versions are past end of life; the most recent to reach it, 2.5.76.0, did so on September 1, 2026. The full Microsoft Entra Connect lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| Azure AD Connect 1.x | — | — | Not published | Past EOL | EOL |
| 2.3.2.0 | 2.3.2.0 | Dec 12, 2023 | Apr 30, 2025 | 528 days past EOL | EOL |
| 2.3.6.0 | 2.3.6.0 | Feb 21, 2024 | Apr 30, 2025 | 528 days past EOL | EOL |
| 2.3.8.0 | 2.3.8.0 | Apr 1, 2024 | Apr 30, 2025 | 528 days past EOL | EOL |
| 2.3.20.0 | 2.3.20.0 | Jul 15, 2024 | Apr 30, 2025 | 528 days past EOL | EOL |
| 2.4.18.0 | 2.4.18.0 | Oct 7, 2024 | Oct 9, 2025 | 366 days past EOL | EOL |
| 2.4.21.0 | 2.4.21.0 | Oct 9, 2024 | Nov 15, 2025 | 329 days past EOL | EOL |
| 2.4.27.0 | 2.4.27.0 | Nov 14, 2024 | Jan 15, 2026 | 268 days past EOL | EOL |
| 2.4.129.0 | 2.4.129.0 | Jan 15, 2025 | Mar 27, 2026 | 197 days past EOL | EOL |
| 2.4.131.0 | 2.4.131.0 | Mar 27, 2025 | May 26, 2026 | 137 days past EOL | EOL |
| 2.5.3.0 | 2.5.3.0 | May 27, 2025 | Jul 31, 2026 | 71 days past EOL | EOL |
| 2.5.76.0 | 2.5.76.0 | Jul 31, 2025 | Sep 1, 2026 | 39 days past EOL | EOL |
| 2.5.79.0 | 2.5.79.0 | Sep 1, 2025 | Oct 23, 2026 | 13 days remaining | Warning |
| 2.5.190.0 | 2.5.190.0 | Nov 19, 2025 | Feb 2, 2027 | 115 days remaining | Warning |
| 2.6.1.0 | 2.6.1.0 | Feb 2, 2026 | Mar 10, 2027 | 151 days remaining | Warning |
| 2.6.3.0 | 2.6.3.0 | Mar 10, 2026 | Jul 7, 2027 | 270 days remaining | Active |
| 2.6.84.0 | 2.6.84.0 | Jul 7, 2026 | Sep 16, 2027 | 341 days remaining | Active |
| 2.6.91.0 | 2.6.91.0 | Sep 16, 2026 | Sep 23, 2027 | 348 days remaining | Active |
| 2.6.92.0 | 2.6.92.0 | Sep 23, 2026 | TBD | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/microsoft-entra-connect)
Microsoft Entra Connect lifecycle status — the real story
Microsoft Entra Connect (Entra Connect Sync, formerly Azure AD Connect) is the server installed on-premises that synchronises on-premises Active Directory identities to Microsoft Entra ID for hybrid identity. Every release is a full version number, and Microsoft publishes a retirement date for each 2.x version on the Connect version history page.
Since March 2023 every 2.x version retires 12 months after a newer version is released, so the newest version has no end date until its successor ships. Microsoft has also retired versions early to align with security changes, as it did for the 2.3 releases. All 1.x versions (Azure AD Connect V1) are unsupported and no longer synchronise at all.
With a retirement date roughly a year after each new release, an Entra Connect server that is installed once and left alone falls out of support quickly, even though it sits in the identity tier. Microsoft's guidance on the version history page is to always install the latest version for new installs and to upgrade to the latest version before the current one retires.
Microsoft Entra Connect release and support pattern
Across the 18 release lines with a published release date, Microsoft Entra Connect has shipped a new line roughly every 2 months (median interval). A line typically stays supported for about 1.2 years from its release to its end-of-life date (measured on the 17 lines with both dates published).
Of the 19 release lines tracked, 12 are past end of life and 7 are still within support; 1 is marked end of life without a published date. The newest line, 2.6.92.0, was released September 23, 2026. The next scheduled end of life is 2.5.79.0 on October 23, 2026 — 13 days from this build. The longest-supported line currently published is 2.6.91.0, to September 23, 2027.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
What does Microsoft Entra Connect end of life mean for your organization?
When a version of Microsoft Entra Connect reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL Microsoft Entra Connect should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when Microsoft Entra Connect reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Microsoft Entra Connect versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Microsoft Entra Connect has 12 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for Microsoft Entra Connect is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."